Property mapping is split among the following worksheets: PropertiesMapping, XDataProperties and UDASmapping.

Properties Mapping

In this worksheet, the Field Name column (column F) is mapped to a Base Class Name (column G) and Property Name (Column H) from the OpenPlant Schema.

Values for the Field Name can come directly from the AVEVA P&ID DWG XData elements or by using the XDataProperties mapping worksheet.

"Field Name" with the value "ItemType" exists by default for all components and contains a Symbol name for leaf classes or PIDtype description for base classes, and can be mapped to any OpenPlant property (Examples: NOTES or DESCRIPTION).

XDataProperties

The XDataProperties sheet helps to make mapping names more easily readable and to add an internal iModel Bridge for the AVEVA P&ID Field Name of each DWG field.

Additionally, the Field names of different AVEVA versions can be joined by XDataProperties and be mapped by the same 'Field name'.

Tip: Alternatively, the DWG field can be mapped directly in PropertiesMapping, Example: PFL.F0.

UDAS mapping

The User Defined Attribute Set (UDAS) is set on this worksheet. It is recommended that the values in UDASmapping be modified for each project as these values are potentially different for each project.

The "Project" column should be always filled. Values can be: "default" string or project number (as defined in the AVEVA project settings and stored in each AVEVA P&ID DWG file).

• 'Field Name' is always a 'DS_' prefix + user attribute name.
• 'Property Name' is a mapped OpenPlant property name.
• 'TypeName' specifies Units of Measure for double values, that are used in original DWG file.
• Proper 'TypeName' mapped value is a Unit TypeName from Units.ecschema.xml.
• Attribute 'TypeName' is required for those OpenPlant Functional properties, for which kind of quantity is set in the OpenPlant Process Functional schema, otherwise the property cannot be mapped.